Systems and methods for vehicle policy enforcement

ABSTRACT

This disclosure relates to systems and methods for vehicle policy management and enforcement. In certain embodiments, a method for enforcing a policy may include receiving policy information at a device including one or more conditions relating to a policy-managed location in a vehicle. A determination may be made whether the device is within the policy-managed location based on signals received by a short-range communication system included in the device and/or the vehicle. The received policy information may be evaluated to determine and implement one or more device actions associated with the one or more conditions.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/173,433, filed Jun. 3, 2016, which is a continuation of U.S. patentapplication Ser. No. 13/769,357, filed Feb. 17, 2013, which claims thebenefit of priority under 35 U.S.C. § 119(e) to U.S. Provisional PatentApplication No. 61/600,572, filed Feb. 17, 2012, and entitled “SYSTEMSAND METHODS FOR VEHICLE POLICY ENFORCEMENT,” all of which are herebyincorporated by reference in their entireties.

COPYRIGHT AUTHORIZATION

Portions of the disclosure of this patent document may contain materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the U.S. Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND AND SUMMARY

The present disclosure relates generally to systems and methods forvehicle policy management and enforcement. More specifically, thepresent disclosure relates to systems and methods for creating,managing, evaluating, and/or enforcing policies in connection withvehicles and other systems.

Driving while distracted is one of the largest contributors toaccidents, injury and death on roadways today. One of the contributingfactors to driving while distracted is the use of mobile devices (e.g.,smartphones, etc.) while operating a vehicle. According to the U.S.National Highway Transportation Safety Board, in 2009 alone, nearly5,500 people were killed and 450,000 more were injured in vehiclecrashes in the U.S. caused by distracted driving. Further, according tothe U.S. Department of Transportation and the Virginia TechTransportation Institute, text messaging on a mobile device whiledriving increases the risk of a crash by nearly 23 times over drivingwhile not distracted.

Sending or receiving a text message on a mobile device may take adriver's eyes off the road for an average of 4.6 seconds, theequivalent—at 55 miles per hour—of driving the length of an entirefootball field blind. Distracted driving in many instances isparticularly concentrated within the younger age segment of thepopulation—especially teens. Distracted driving is also an issue inother contexts, including in the operation of public transit vehicles(e.g., busses, trains, airplanes, etc.). With the widespreadproliferation of mobile devices, distracted driving is a growingproblem. Accordingly, systems and methods that reduce distracteddriving, protect others from distracted driving, and/or otherwiseenhance vehicle safety or control are desirable.

Embodiments of the systems and methods disclosed herein relate tocreating, managing, evaluating, and/or enforcing policies in connectionwith vehicles and other systems to enhance vehicle safety and/or control(e.g., by reducing distracted driving). In certain embodiments, a methodfor enforcing a policy on a device associated with a vehicle (e.g., amobile phone) may include receiving policy information at the deviceincluding one or more conditions relating to a policy-managed locationin the vehicle (e.g., a driver's seat location). The policy informationmay further include one or more exceptions associated with the one ormore conditions.

A determination may be made whether the device is within thepolicy-managed location based on signals received by a short-rangecommunication system included in the device and/or the vehicle. Thereceived policy information may be evaluated to determine and implementone or more device actions associated with the one or more conditions.Device actions may include, without limitation, disabling a feature orapplication of the device, changing an operating mode of the device,and/or the like. In certain embodiments, the policy information mayfurther be evaluated based on sensor information received from one ormore sensors included in the device and/or contextual informationreceived from the vehicle.

In further embodiments, a method for enforcing a policy on a vehicleand/or a system included in the vehicle may include receiving policyinformation including one or more conditions relating to apolicy-managed location in the vehicle (e.g., a driver's seat location)at a policy management system included in the vehicle. The policyinformation may further include one or more exceptions associated withthe one or more conditions.

A determination may be made whether a device (e.g., a mobile phone) iswithin the policy-managed location based on signals received by ashort-range communication system included in the device and/or thevehicle. The received policy information may be evaluated to determineand implement one or more vehicle actions associated with the one ormore conditions. Vehicle actions may include, without limitation,disabling a feature of the vehicle, storing event information relatingto the presence of the device within the policy-managed location,providing one or more notifications (e.g., audible or visual), and/orthe like. In certain embodiments, the policy information may further beevaluated based on sensor information received from one or more sensorsincluded in the vehicle and/or contextual information received from thedevice.

BRIEF DESCRIPTION OF THE DRAWINGS

The inventive body of work will be readily understood by referring tothe following detailed description in conjunction with the accompanyingdrawings, in which:

FIG. 1a illustrates a vehicle equipped with an exemplary communicationsystem consistent with embodiments of the present disclosure.

FIG. 1b illustrates a vehicle equipped with another exemplarycommunication system including a plurality of elements consistent withembodiments of the present disclosure.

FIG. 2 illustrates an exemplary vehicle and device consistent withembodiments of the present disclosure.

FIG. 3a illustrates an exemplary policy-enforced mode of operation in adevice and a vehicle consistent with embodiments of the presentdisclosure.

FIG. 3b illustrates another exemplary policy-enforced mode of operationin a device and a vehicle consistent with embodiments of the presentdisclosure.

FIG. 4a illustrates exemplary policy-enforced device actions consistentwith embodiments of the present disclosure.

FIG. 4b illustrates exemplary policy-enforced vehicle actions consistentwith embodiments of the present disclosure.

FIG. 5 illustrates a flow chart of an exemplary device-based method ofdetermining the presence of a device in a particular location within avehicle consistent with embodiments of the present disclosure.

FIG. 6 illustrates exemplary generation and distribution of policy datato a device consistent with embodiments of the present disclosure.

FIG. 7 illustrates a flow chart of an exemplary device policy evaluationand enforcement process consistent with embodiments of the presentdisclosure.

FIG. 8 illustrates a flow chart of an exemplary vehicle-based method ofdetermining the presence of a device in a particular location within thevehicle consistent with embodiments of the present disclosure.

FIG. 9 illustrates exemplary generation and distribution of policy datato a vehicle consistent with embodiments of the present disclosure.

FIG. 10 illustrates a flow chart of an exemplary vehicle policyevaluation and enforcement process consistent with embodiments of thepresent disclosure.

FIG. 11 illustrates exemplary condition-based policy enforcement actionsconsistent with embodiments of the present disclosure.

FIG. 12 illustrates exemplary generation and distribution of policy databy a supervising entity to a device and a vehicle consistent withembodiments of the present disclosure

FIG. 13 illustrates exemplary information used in a device-based policymanagement and enforcement decision consistent with embodiments of thepresent disclosure.

FIG. 14 illustrates exemplary information used in a vehicle-based policymanagement and enforcement decision consistent with embodiments of thepresent disclosure.

FIG. 15 illustrates exemplary vehicle sensors that can be used in policyevaluation and enforcement processes consistent with embodiments of thepresent disclosure.

FIG. 16 illustrates exemplary supplemental device data that can be usedin policy evaluation and enforcement processes consistent withembodiments of the present disclosure.

FIG. 17 illustrates exemplary supplemental vehicle data that can be usedin policy evaluation and enforcement processes consistent withembodiments of the present disclosure.

FIG. 18 illustrates exemplary generation of contextual vehicle anddevice data consistent with embodiments of the present disclosure.

FIG. 19 illustrates exemplary policy evaluation and enforcement by avehicle consistent with embodiments of the present disclosure.

FIG. 20 illustrates exemplary policy evaluation and enforcement by adevice consistent with embodiments of the present disclosure.

FIG. 21 illustrates data distribution to and from third parties that maybe used in policy evaluation and enforcement processes consistent withembodiments of the present disclosure.

FIG. 22 illustrates exemplary device and vehicle actions in response topolicy evaluation and enforcement decisions consistent with embodimentsof the present disclosure.

FIG. 23 illustrates various exemplary credentials for providing securepolicy generation, management, and/or enforcement consistent withembodiments of the present disclosure.

FIG. 24 illustrates an exemplary system that may be used to implementembodiments of the systems and methods of the present disclosure.

DETAILED DESCRIPTION

A detailed description of systems and methods consistent with theinventive body of work is provided below. While several embodiments aredescribed, it should be understood that the disclosure is not limited toany one embodiment, but instead encompasses numerous alternatives,modifications, and equivalents. In addition, while numerous specificdetails are set forth in the following description in order to provide athorough understanding of the embodiments disclosed herein, someembodiments can be practiced without some or all of these details.Moreover, for the purpose of clarity, certain technical material that isknown in the related art has not been described in detail in order toavoid unnecessarily obscuring the disclosure.

Embodiments of the disclosure may be understood by reference to thedrawings, wherein like parts may be designated by like numerals. Thecomponents of the disclosed embodiments, as generally described andillustrated in the figures herein, could be arranged and designed in awide variety of different configurations. Thus, the following detaileddescription of various embodiments is not intended to limit the scope ofthe disclosure, as claimed, but is merely representative of possibleembodiments. In addition, the steps of methods disclosed herein do notnecessarily need to be executed in any specific order, or evensequentially, nor need the steps be executed only once, unless otherwisespecified.

Mobile devices (e.g., smartphones) often include a panoply of featuresand sensor systems. For example, many mobile devices may includeaccelerometers, Global Positioning System (“GPS”) sensors, wirelesscommunication systems (e.g., Bluetooth®, WiFi, near field communication(NFC) technology, etc.), and/or the like. Systems and methods disclosedherein may use one or more device sensors and/or communication systemsin connection with managing and enforcing policies associated withdevices and/or vehicles to reduce distracted driving and/or other unsafebehavior. For example, a device may include a policy articulating thatwhen the device is moving at speeds associated with driving, certainfeatures of the device may not be used. GPS sensors and/oraccelerometers included in the device may be used to determine when thedevice is moving at such speeds and, in response, policy enforcementsystems operating on the device may prevent certain device features(such as text messaging, electronic mail, keyboard entry of data, etc.)from being used.

While such a simplistic policy may help to reduce distracted driving, incertain circumstances it may not account for instances when a device isin motion but is still safe to use. For example, if a rear seatpassenger in a vehicle or a rider on a public transit vehicle wishes touse their device while in motion, they can do so safely. Accordingly,systems and methods disclosed herein may detect when a device is beingused in unsafe circumstances or when a device is in an environment whereits use would be unsafe, and may trigger one or more responsive actionsthat can help reduce risk (e.g., warning a device user of safetyconcerns, warning others who may be impacted by an unsafe situation,disabling device features that may contribute to distractions, and/orthe like).

Mobile devices (e.g., smartphones) may include short-range communicationcapabilities. Systems and methods disclosed herein may use short-rangecommunication capabilities to manage and enforce policies that encouragesafe driving practices. For example, in certain embodiments, short-rangecommunication technologies can be used to locate one or more mobiledevices within a vehicle, and such location information can be used tomore accurately determine whether the device and/or vehicle can be, oris being, used safely.

FIG. 1a illustrates a vehicle 100 equipped with an exemplarycommunication system consistent with embodiments of the presentdisclosure. Although FIG. 1a illustrates vehicle 100 as a passengervehicle, systems and methods disclosed herein may be used in connectionwith any suitable land, water, and/or air vehicle including, withoutlimitation, cars, trucks, busses, motorcycles, bicycles, trains, boats,aircraft, and/or the like.

The vehicle 100 may include a short-range communicationsreceiver/transmitter element 101. In certain embodiments, thereceiver/transmitter element 101 may be located proximate to a driver ofthe vehicle 100. For example, as illustrated, the receiver/transmitterelement 101 may be located in or near a steering wheel of the vehicle100. In further embodiments, the receiver/transmitter element 101 may belocated proximate to any other location in the vehicle 100 associatedwith policy management and enforcement decisions. For example, if abackseat passenger-side location in the vehicle 100 is associated withpolicy management and enforcement decisions, one or morereceiver/transceiver elements 101 may be located proximate to thebackseat passenger-side location of the vehicle 100.

In certain embodiments, the short-range communicationsreceiver/transmitter element 101 may produce a field that encompasses apolicy-managed location within the vehicle 100. For example, asillustrated, receiver/transmitter element 101 may produce a field thatencompasses a driver's seat location within the vehicle 100. Theshort-range communications receiver/transmitter element 101 may beconfigured to detect and/or communicate with one or more devices (notshown) located within the field associated with the policy-managedlocation. Similarly, devices may be able to detect their presence withina field associated with the policy-managed location. For example,receiver/transmitter element 101 and/or a device may be able to detectwhen the device is located within a field produced byreceiver/transmitter element 101 associated with the driver's positionwithin the vehicle 100.

The short-range communications receiver/transmitter element 101 may useany suitable short-range communication technologies and/or protocols tocommunicate with a device (e.g., a smartphone) located in or near thevehicle 100 within a range of the receiver/transmitter element 101. Forexample, the receiver/transmitter element 101 may use active and/orpassive short-range communication technologies, near field communication(“NFC”) standards or technologies, IEEE's 802.11 standards, Bluetooth®,ultra-wide band (“UWB”), Zigbee®, Radio-frequency identification(“RFID”), and/or any other suitable wireless communication protocols orcombinations thereof. In some embodiments, modified versions ofstandardized technologies may be used to, for example, increase (ordecrease) the range or accuracy of the signal, vary the frequency thatis used, and/or the like. Thus, for ease of explanation, when referenceis made herein to a particular standard or protocol, it will beunderstood that such modified versions or extensions of the standard orprotocol are intended to be encompassed as well. For example, whenreference is made herein to near field communication (NFC) technology,it is meant to include technologies that may not literally comply with aformal NFC standard, but which operate in accordance with the same basicphysical principles (e.g., situations where the receiver/transmittershave been modified so that the field may cover a larger area).

In certain embodiments, the receiver/transmitter element 101 may beconfigured to facilitate active communication with one or more deviceswithin the range of the receiver/transmitter element 101. In furtherembodiments, the receiver/transmitter element 101 may passivelydetermine that one or more devices are within a proximate range of thereceiver/transmitter element 101. Thus, it will be appreciated that,unless otherwise clear from the context, the term “receiver/transmitter”is used herein to refer to elements capable of acting as both a receiverand a transmitter, as well as elements that are capable of acting as areceiver (but not a transmitter), and elements that are capable ofacting as a transmitter (but not a receiver).

Although, as previously indicated, a variety of communicationstechnologies may be used in conjunction with the systems and methodsdescribed herein, technologies based on near field communications (NFC)may be particularly advantageous for some embodiments where it isespecially desirable to precisely determine the location of the devicewithin a small region (such as a vehicle passenger compartment). NFCtechnologies have an added advantage in that coupling can typicallyoccur only within a specific (typically short) distance from the antenna(e.g., the “near field”). Therefore, by placing one or more antennas atknown location(s), it is possible to easily (and with a considerabledegree of confidence) infer the location of the device that is beingcommunicated with. Furthermore, passive near field communications hasthe added benefit of low battery drain on the portable device (whiletaking advantage of the more plentiful power source on the vehicle); andactive near field communication can be employed to communicatedynamically-changing data in a bi-directional fashion (such as operatingmode information sent in a message request-response sequence).Representative near field communications technologies that can be usedinclude those that have been specified by industry standardsorganizations such as the NFC Forum, ECMA, ETSI, ISO/IEC, as well asother more general applications of near field communication technology,that employ different frequencies, signal strengths, thresholds and/ordata protocols. Ideally, frequencies, signal strengths, and thresholdswould be customized to produce a near-field that occupies a volume ofspace corresponding to the size of the intended policy-managed location.However, any number of antennas and their associated near fields (ofsimilar or different sizes) may be suitably arranged to encompass avolume of whatever shape or size is desired.

FIG. 1b illustrates a vehicle 100 equipped with another exemplaryshort-range communication system including a plurality of elements 101a, 101 b consistent with embodiments of the present disclosure. Incertain embodiments, to increase a size of a field emitted by theshort-range communication system (e.g., to increase a coverage volume)and/or to increase positional sensing accuracy, the communication systemmay include a plurality of receiver/transmitter elements 101 a, 101 b.For example, as illustrated, the short-range communication system mayinclude a first receiver/transmitter element 101 a located above thedriver position and a second receiver/transmitter element 101 b locatedbelow the driver position.

Any suitable number and/or configuration of receiver/transmitterelements may also be located at various points within the vehicle 100 tocommunicate with devices (not shown) and/or determine location(s) ofdevices within the vehicle 100. For example, one or morereceiver/transmitter elements may be associated with each seat locationin the vehicle 100, thereby enabling the short-range communicationsystem to determine how many devices are located in the vehicle 100 andthe location of the devices relative to the one or more seat locations.Exemplary locations for receiver/transmitter elements include, withoutlimitation, the vehicle dashboard, the vehicle console area, in or neardriver and/or passenger visors, headrests, seatbelt components, and/orany location that is practicable and suitably allows areceiver/transmitter element to cover a designated volume of space(e.g., a policy-managed location) within the vehicle 100.

In certain embodiments, using a plurality of receiver/transmitterelements 101 a, 101 b may allow a location of a device within thevehicle 100 to be determined based on relative signal strengths providedand/or received by receiver/transmitter elements 101 a, 101 b. Forexample, if a device receives a signal from receiver/transmitter element101 a that is stronger than a signal received from receiver/transmitterelement 101 b, it may be determined that the device is located closer toelement 101 a than it is to element 101 b. Similarly, ifreceiver/transmitter element 101 a receives a signal from a device thatis stronger than a signal received from receiver/transmitter element 101b, it may be determined that the device is located closer to element 101a than it is to element 101 b. Based on the locations of thereceiver/transmitter elements 101 a, 101 b relative to one or morelocations within the vehicle 100, a position or likely position of thedevice relative to the one or more locations within the vehicle 100 maybe determined.

In some embodiments, the relative signal strengths betweenreceiver/transmitter elements 101 a, 101 b and a device may be used totriangulate a position or likely position of the device within thevehicle 100. In some embodiments, communication delay times between adevice and a plurality of receiver/transmitter elements 101 a, 101 b maybe used to determine which of the plurality of elements 101 a, 101 b thedevice is closest to and/or to triangulate a position of the devicewithin a vehicle 100.

FIG. 2 illustrates an exemplary vehicle 100 and device 200 consistentwith embodiments of the present disclosure. Although illustrated as asmartphone, device 200 may comprise a variety of computing devicesand/or systems, including any mobile system and/or device suitable toimplement the systems and methods disclosed herein. For example, device200 may comprise a laptop computer system, a wireless communicationdevice (e.g., a cellular telephone such as a smartphone or featurephone), a tablet computer, a wireless control device (e.g., keylessentry or remote start devices), a gaming or other entertainment device,and/or the like. Additional non-limiting examples of device 200 includea telematics system, a navigational system, and/or an in-vehicleinfotainment (“IVI”) system, which may or may not be integrated into thevehicle 100.

The device 200 may include a short-range communications system includingone or more receiver/transmitter elements 201. The receiver/transmitterelement(s) 201 may use any suitable short-range communicationtechnologies and/or protocols to communicate with one or morereceiver/transmitter elements 101 associated with the vehicle 100. Forexample, the receiver/transmitter element 201 may use active and/orpassive short-range communication technologies, NFC standards, IEEE's802.11 standards, Bluetooth®, UWB, Zigbee®, RFID, and/or any othersuitable wireless communication protocols or combinations thereof toenable the vehicle 100 and/or the device 200 to detect one anotherand/or to communicate data. For example, the receiver/transmitterelement 201 may allow the device 200 to determine when it is located ina particular policy-managed location within the vehicle 100 (e.g., adriver position). Utilizing this information, the device 200 and/or thevehicle 100 may evaluate and enforce policies regarding the use of thedevice 200 and/or the vehicle 100 under one or more conditions.

FIG. 3a and FIG. 3b illustrate exemplary policy-enforced modes ofoperation in a device 200 and a vehicle 100 consistent with embodimentsof the present disclosure. Policies may articulate one or more rules orconditions relating to the use and/or function of the vehicle 100 and/orthe device 200. For example, policies may enforce, among other things,conditions relating to the vehicle 100 and/or the device 200 (e.g.,device location-based conditions, vehicle location-based conditions,vehicle use conditions, etc.), actions associated with the one or moreconditions (e.g., disable text messaging applications and/or otherdevice features when vehicle 100 is moving, disable starting motor orother vehicle 100 features, cause emergency indicator lights of vehicle100 to flash, etc.), exceptions to actions, and/or the like. In certainembodiments, policies may be used to enforce one or more modes ofoperation of a device 200 and/or a vehicle 100 based on the occurrenceof one or more conditions.

Policies may be device-based and/or vehicle-based. A device policy mayarticulate policies regarding the use and/or function of the device 200under one or more conditions. As illustrated in FIG. 3a , a devicepolicy may specify an action by device 200 in response to the occurrenceof one or more conditions. For example, a device policy may provide thata text messaging application of a device 200 should be disabled when itis determined (e.g., by the device, the vehicle, and/or a combination ofboth or other means) that the device is within a driver's position (orother policy-managed location) of the vehicle 100.

A vehicle policy may articulate certain policies regarding the useand/or function of the vehicle 100 under one or more conditions. Asillustrated in FIG. 3b , a vehicle policy may articulate an action byvehicle 100 in response to the occurrence of one or more conditions. Forexample, a vehicle policy may provide that a starter motor of thevehicle 100 should be disabled when the vehicle 100 determines that thedevice 200 and/or a feature thereof is being used in a driver's positionof the vehicle 100.

In certain embodiments, policies may be both device-based andvehicle-based. That is, a policy may articulate certain actions to beperformed by both the vehicle 100 and the device 200 in response to theoccurrence of one or more conditions. For example, a policy may providethat under certain conditions, the device 200 should perform certainresponsive actions (e.g., disabling certain features, etc.) and thevehicle 100 should perform certain responsive actions (e.g., warningoccupants of the vehicle, other drivers, and/or law enforcement ofunsafe driving practices, etc.). In certain embodiments, such policiesmay be enforced independently and/or simultaneously by the vehicle 100and/or the device 200.

Policies associated with the vehicle 100 and the device 200 may furtherbe articulated and/or enforced, at least in part, independently. Forexample, the device 200 may detect that it is within a policy-managedlocation within the vehicle 100 (e.g., a driver's position). Inresponse, the device 200 may switch to a safer mode of operation (e.g.,a “voice control only” mode or the like). Subsequently, uponindependently sensing that the device 200 is in a safer mode ofoperation, the vehicle 100 may perform an appropriate responsive action(e.g., disengaging a warning buzzer or the like).

FIG. 4a illustrates exemplary policy-enforced device actions 400consistent with embodiments of the present disclosure. As discussedabove, a policy (e.g., a device-based policy) may express certainactions 400 to be performed by a device 200 in response to theoccurrence of one or more conditions. For example, a device may take oneor more device actions 400 in response to determining that the device200 is within a policy-managed location within a vehicle 100. Deviceactions 400 may include, for example, storing information regarding theuse of the device 200 while in a policy-managed location (e.g., timeand/or date, types of usage, devices and/or applications used, etc.). Incertain embodiments, the device actions 400 may include locking ordisabling, temporarily or otherwise, certain features and/orfunctionalities of the device 200. For example, certain communicationfeatures such as cellular radio communications, data services, textmessaging communications, and/or the like may be temporarily locked ordisabled. Similarly, certain device applications such as text messagingapplications, e-mail applications, instant message (“IM”) applications,and/or any other application may be temporarily locked or disabled.Certain device functions may also be temporarily locked or disabled,including device 200 keyboards, screens, and/or other systems orservices.

Device actions 400 may further include automatic reply messaging inresponse to incoming communications. For example, if a text message isreceived by the device 200 while it is in a policy-managed locationwithin the vehicle 100 (e.g., a driver's position), the device mayautomatically send a responsive message (e.g., “I'm driving now, I willget back to you later” or the like). In certain embodiments, suchautomatic reply messages may be configurable by a user and may includefurther information derived from other vehicle 100 and/or device 200systems (e.g., a GPS system) such as an estimated arrival time to adestination.

In certain embodiments, device actions 400 may be associated with one ormore modes of operation of device 200. Responsive to the occurrence ofone or more policy-defined conditions, the device 200 may enter one ormore modes of operation. Device modes of operation may include, withoutlimitation, a “voice control mode,” a “driving mode,” a “hands freemode,” an “airplane mode,” a “silent mode,” and/or any other suitableoperational mode. In certain embodiments, a mode of operation of thedevice 200 may be associated with the activation and/or disabling of acertain set of features of the device 200 (e.g., features contributingto driver distraction). For example, in some embodiments, while in a“driving mode,” a keyboard, screen, and/or certain applications of thedevice 200 may be disabled, and the device 200 may only be controlledusing voice commands.

While several device actions 400 and/or modes of operation are describedherein, the disclosed actions and/or modes of operation are not to beconsidered limiting. Rather, the disclosed device actions 400 and/ormodes of operation are to be viewed as examples of possible deviceactions 400 and/or modes of operation, as many other device actions 400and/or modes of operation may be implemented alternatively or inaddition as part of the device-based policies disclosed herein.

FIG. 4b illustrates exemplary policy-enforced vehicle actions 402consistent with embodiments of the present disclosure. As discussedabove, a policy (e.g., a vehicle-based policy) may express certainactions 402 to be performed by a vehicle 100 in response to theoccurrence of one or more conditions. For example, a vehicle 100 maytake one or more vehicle actions 402 in response to determining that adevice 200 is within a policy-managed location within the vehicle 100(e.g., in a driver's position). Vehicle actions 402 may include, forexample, storing information regarding the use of the device 200 and/orthe vehicle 100 while the device 200 is in a policy-managed location inthe vehicle 100 (e.g., time and/or date, vehicle speed, vehicledrivetrain status—drive, park, etc., vehicle location, etc.)

In certain embodiments, vehicle actions 402 may include providing one ormore notifications. Notifications may include audible or visualnotifications or any combination thereof. For example, the vehicle 100may sound an audible warning (e.g., a buzzer or the like) similar towhat occurs when a vehicle occupant is detected in a seat with anunsecured seatbelt. Notifications may also be provided external to thevehicle 100. For example, the vehicle 100 may dim or flash one or morehead and/or taillights, thereby warning nearby traffic or pedestrians ofa possible distracted driver.

In some embodiments, vehicle actions 402 may further includetransmitting certain information and/or messages to one or more entitiesassociated with the vehicle 100 and/or the device 200. For example, inresponse to determining that the device 200 is being used in apolicy-managed location, vehicle 100 may transmit a notification to alaw enforcement agency, an insurance provider, a supervising entity(e.g., fleet operators, concerned parents, etc.), and/or otherinterested entities indicating that the device 200 is being used in apolicy-managed location within the vehicle 100.

In further embodiments, the vehicle actions 402 may include locking ordisabling, temporarily or otherwise, certain features and/orfunctionalities of the vehicle 100. For example, a starter motor of thevehicle 100 and/or the ability of a driver to engage the powertrain ofthe vehicle 100 may be temporarily disabled based on a determinationthat a device 200 is being used in a policy-managed location within thevehicle 100 and/or in a policy-managed situation (e.g., while a publictransit vehicle is in service, etc.). Such features and/orfunctionalities may be re-enabled when use of the device 200 within thepolicy-managed location or situation ceases.

Similar to device actions 400, vehicle actions 402 may also beassociated with one or more modes of operation of vehicle 100 (e.g.,park, drive, driving under certain speeds, etc.). While several vehicleactions 402 and/or modes of operation are disclosed herein, the actionsand/or modes of operation disclosed herein are to be considered asexamples of possible vehicle actions 402 and/or modes of operations, asmany other types of vehicle actions 402 that may be implemented as partof vehicle-based policies are also contemplated.

FIG. 5 illustrates a flow chart of an exemplary device-based method ofdetermining the presence of a device in a particular location within avehicle and/or in a particular policy-managed situation. Particularly,the illustrated method may determine the presence of a device in apolicy-managed location (e.g., a sensitive location). As used herein,the terms policy-managed location and sensitive location may be usedinterchangeably. It will also be understood that while, for ease ofexplanation, many of the examples set forth herein refer simply to theapplication of location-based policies, situation-based (or mode ofoperation-based) policies can be applied alternatively or in addition.The illustrated method may be implemented by a device in a variety ofways, including using software, firmware, hardware, and/or anycombination thereof.

Referring once again to FIG. 5, at 202, the method may be triggered. Incertain embodiments, the method may be triggered as part of a routinestart-up process of a device. Alternatively, or in addition, the methodmay be triggered as a result of opening a particular application orusing a certain feature of the device (e.g., a text messagingapplication or a device keyboard, using the device to unlock thevehicle, etc.) and/or based on the occurrence of a particular deviceevent (e.g., receiving an incoming communication such as a textmessage). In further embodiments, the method may be triggered based on adetermination by the device and/or associated sensors (e.g., GPSsensors, accelerometers, and/or the like) that the device is in asituation where policy management is desirable. For example, the methodmay be triggered based on the device determining that it is locatedwithin a moving vehicle, that the vehicle is moving over a certainspeed, that the vehicle is operating at a certain time of day or incertain weather or road conditions, that the vehicle is being driven bya specific driver and/or occupied by certain passengers, and/or anyother suitable situation or combination of situations.

At 203, the device may check for signals from a short-rangecommunication system in proximity to the device. Checking for signalsfrom a short-range communication system may result in a variety ofoutcomes. For example, no signals may be received, signal(s) may bereceived that do not indicate that the device is in a policy-managedlocation in the vehicle, or signal(s) may be received that indicate thatthe device is in a policy-managed location in the vehicle (e.g., adriver's position or other sensitive position). For example,vehicle-based short range transmitters can securely transmit a signalthat indicates to the device that it is in proximity to a sensitivearea, and possibly communicate additional data to indicate what type ofarea the device is operating in. As another example, in some embodimentsone or more vehicle sensors can be used to locate the source of wirelesssignals from the device (e.g., signal strength, differential signalstrength, or disruptions to a field that can be sensed by the vehicle,and communicated to the device). Another example of how a determinationcould be made as to whether a device is in a sensitive location is bymaking use of device and/or vehicle sensors and/or tags that mayactively or passively communicate using Near Field Communication links,thereby passing data relevant to device location, vehicle status, and/ordevice status to one another. In yet another example, a device canmonitor signal strength from one or more standardized vehicle-mountedbeacons, and/or make a comparison of signal characteristics frommultiple beacons placed at specific locations within the vehicle. Itwill be appreciated that any or all of the foregoing example techniques,as well as any other suitable technique(s), could be used to determinedevice location.

Referring once again to FIG. 5, based at least in part on the receivedsignals, at 204, the device may determine whether it is proximate toand/or within a policy-managed location. If the device is in apolicy-managed location, device location information 206 may be set toindicate that the device is in a sensitive and/or policy-managedlocation at 205. If the device is not in a policy-managed location, thedevice location information 206 may be set to indicate that the deviceis not in a sensitive and/or policy-managed location at 207. In furtherembodiments, if the device is not proximate to a policy-managed locationbut proximate to another known location, the known location may beincluded in the device location information 206 set at 207.

After the device location information 206 has been set, the method mayproceed to 208 where the device may wait for a certain delay time and/orthe receipt of a re-detection trigger, enabling the device to re-checkits position on a periodic and/or an event-driven basis. For example,when a vehicle operator leaves the vehicle, he or she may wish to use adevice in a normal manner without any policy-enforced encumbrancesassociated with the device being located within a policy-managedlocation. Waiting for a certain delay period and/or for the receipt ofthe re-detection trigger event may allow the device location information206 to be updated to reflect a current location status of the device.For example, the method may be re-triggered when an application islaunched on the device and/or a screen of the device is activated. Byutilizing a time delay based re-triggering process, an event-basedre-triggering process, or a combination thereof, battery life of thedevice may be conserved in comparison to other embodiments of thesystems and methods disclosed herein where location information ismonitored on an effectively continuous basis (e.g., without a delay timeor re-triggering event).

Consistent with embodiments disclosed herein, device locationinformation 206 may be used in policy management and enforcementprocesses. For example, as discussed above, certain features and/orfunctions of a device and/or a vehicle may be temporarily disabled (orenabled and/or actuated) based on the status of the device locationinformation 206 in accordance with articulated policies. In addition todevice location information 206, a device and a vehicle may exchangedata that indicates contextual information about the vehicle or itsstatus. As discussed in more detail below, this contextual vehicleinformation may also be used in policy management and enforcementprocesses disclosed herein.

FIG. 6 illustrates exemplary generation and distribution of policy data209 to a device 200 consistent with embodiments of the presentdisclosure. Policy data 209 may specify and/or otherwise express orenable enforcement of one or more rules or conditions relating to theuse and/or function of the device 200. For example, policy data 209 mayexpress, encode, and/or otherwise be used to facilitate the enforcementof, among other things, conditions relating to the device 200 (e.g.,device location-based conditions, vehicle location-based conditions,device use conditions, etc.), actions associated with the one or moreconditions (e.g., disable text messaging applications and/or otherdevice features when vehicle is moving, etc.), exceptions to actions,and/or the like.

Policy data 209 may be delivered to a device 200 in a variety of ways.In certain embodiments, policy data 209 may be pre-set in a device 200(e.g., by a device manufacturer or the like). In further embodiments,policy data 209 (e.g., conditions, actions, exceptions, etc.) may beconfigurable via any suitable means or combination thereof. For example,in some embodiments, policy data 209 may be set and/or configured by auser 602 a (e.g., a device owner or the like) directly into the device200. For example, one or more device inputs (e.g., a keyboard, touchscreen, etc. interacting with one or more menus on a user interface) maybe used to set and/or configure policy data 209.

In further embodiments, a user 602 b may deliver policy data 209 to thedevice 200 via a network 600. The network 600 may comprise a variety ofnetwork communication devices and/or channels and may use any suitablecommunications protocols and/or standards facilitating communicationbetween the device 200 and one or more network-connected entities 602b-610. For example, the network 600 may comprise a wireless carriersystem, such as a personal communications system (“PCS”), a globalsystem for mobile communication, and/or any other suitable communicationsystem incorporating any suitable communication standards and/orprotocols. In further embodiments, the network 600 may include an analogmobile communications network and/or a digital mobile communicationsnetwork utilizing, for example, code division multiple access (“CDMA”),Global System for Mobile Communications or Groupe Speciale Mobile(“GSM”), frequency division multiple access (“FDMA”), and/or timedivisional multiple access (“TDMA”) standards. In certain embodiments,the network 600 may incorporate one or more satellite communicationlinks. In yet further embodiments, the network 600 may use IEEE's 802.11standards, Bluetooth®, ultra-wide band (“UWB”), Zigbee®, and/or anyother suitable standard or standards. In some embodiments, the networkmay comprise the Internet and/or a local WiFi network.

As illustrated, policy data 209 may be delivered to the device 200 froma variety of network-connected entities 602 b-610. For example, asdiscussed above, a user 602 b of the device 200 may deliver policy data209 to the device 200 via the network 600. In certain embodiments, auser 602 b of the device 200 may be a device owner. In furtherembodiments, the user 602 b may be a parent/employer of a device userand/or some other interested party.

In certain embodiments, a mobile service operator 604 may wish to offerthe ability to increase the safety of its customers using devices 200 ontheir network 600 by offering the ability to configure devices 200 foradded safety. Accordingly, mobile service operator 604 may deliverpolicy data 209 to the device 200 via the network 600. In someembodiments, the mobile service operator 604 can deliver policy data 209to device 200 directly or may provide policy management and enforcementservices on behalf of parents/employers or other supervising entitieswho may be their direct customers.

In another example, a policy distribution service 606 may deliver policydata 209 to the device 200 via the network 600. In certain embodiments,the policy distribution service 606 may be associated with a mobiledevice management service or a mobile application developer. In someembodiments, policy distribution service 600 may respond to locationdata (e.g., GPS data) that provides an indication as to the location ofthe device 200 or an associated vehicle, and deliver appropriate policydata 209 based on the location. For example, certain jurisdictions mayhave laws relating to the use of devices 200 while operating a vehicle.Policy distribution service 606 may detect when a device 200 and/or avehicle are within such a jurisdiction and deliver appropriate policydata 209 specifying rules reflecting the laws of the jurisdiction.Similarly, certain locations may have rules or regulations relating tothe use of devices 200 while in the location (e.g., a movie theater).Policy distribution service 606 may detect when a device 200 is at sucha location and deliver appropriate policy data 209 reflecting the rulesor regulations of the location.

In some embodiments, mobile device manufacturers 608 may embed policydata 209 into devices 200 at the time of manufacture and/or, via network600, deliver policy data 209 to a device 200 at a later date (e.g., viaan application that is downloaded to the device, a system update, and/orthe like). In this manner, mobile device manufacturers 608 can perform“late customization” of their devices. That is, mobile devicemanufacturers 608 can ship a device 200 without embedded policy data 209or with default policy data 209, and may later deliver policy data 209that reflects the laws of the jurisdiction where the associated device200 is used and/or that reflects the preferences of the user 602. Inother embodiments, policy data 209 may be embedded at time ofmanufacture or within an application in an inactive state. The policycan later be activated by the user directly or alternatively vianetwork-based mechanisms previously described.

A variety of other sources of policy data 209 are also contemplated. Forexample, policy data 209 may be delivered to a device 200 via thenetwork 600 by a law enforcement agency 610. For example, a lawenforcement agency 610 may deliver policy data 209 to a device 200reflecting the laws of a particular jurisdiction. In yet furtherembodiments, policy data 209 may be delivered by insurance providersthat may offer discounts to drivers that use the policy management andenforcement systems and methods disclosed herein. Accordingly, thesources of policy data 209 detailed herein are to be viewed asillustrative and not exhaustive. In some embodiments, policy data 209may form part of, be embodied as, or otherwise be delivered inconnection with, an application (or “app”) that is downloaded to thedevice 200 from an application store at the request of the device's useror administrator.

The disclosed policy management and enforcements systems and methods maybe used in a variety of devices 200. For example, package deliveryservices such as FedEx may choose to set policy on special-purposedevices such as shipment tracking devices and their use by employeedrivers in delivery vehicles. Similarly, vehicle manufacturers maychoose to set policy on telematics or IVI systems included in vehiclesand their use by vehicle occupants while driving. Thus, it will beappreciated that the policy management and enforcement techniquesdisclosed herein may be used in connection with a variety of devices 200and/or scenarios, not just in connection with the use of mobile phonesin vehicles.

FIG. 7 illustrates a flow chart of an exemplary device policy evaluationand enforcement process consistent with embodiments of the presentdisclosure. The illustrated method may be implemented in a variety ofways, including using software, firmware, hardware, and/or anycombination thereof. The illustrated process may use one or more inputsincluding, without limitation, device location information 206, policydata 209, sensed and/or received data 213, and/or contextual vehicledata 214. It will be appreciated that in other embodiments othercombinations of these or other inputs may be used.

Device location information 206 may include an indication as to wherethe device is located within a vehicle. For example, the device locationinformation 206 may indicate if the device is in a sensitive and/orpolicy managed location and/or another known location in the vehicle. Insome embodiments, the device location information 206 may be generatedusing, at least in part, a short-range communications system included inthe device and/or the vehicle. Policy information 209 may includeinformation regarding one or more conditions used to evaluate whether anaction should occur, actions associated with the conditions, exceptionsto the actions, and/or the like. Sensed and/or received data 213 mayinclude, without limitation, data generated by device sensors (e.g.,parameters associated with functions of the phone, accelerometer data,and/or the like) and/or data received by third parties. Contextualvehicle data 214 may include, without limitation, information receivedfrom a vehicle over a short-range communications system or other meansthat, among other things, may specify environmental data about thevehicle status or other information that is sensed by the vehicle.

At 210, the device policy evaluation and enforcement process may betriggered. In certain embodiments, the method may be triggered as partof a routine start-up process of a device. Alternatively, or inaddition, the method may be triggered as a result of opening aparticular application or using a certain feature of the device (e.g., atext messaging application or a device keyboard) and/or based on theoccurrence of a particular device event (e.g., receiving an incomingcommunication such as a text message). In further embodiments, themethod may be triggered by a short range communication system of thedevice detecting a change in signal status (e.g., indicating that thedevice location has changed) and/or by a change in any of inputs 206,209, 213, and/or 214.

At 211, contextual information used for policy evaluation decisions maybe read or sensed. At 212, policy logic that articulates or operates onpolicy data 209 may be evaluated. As illustrated, this evaluation may bebased, at least in part, on inputs 206, 209, 213, and/or 214. Forexample, a simple policy may specify that if the device locationinformation 206 indicates that the device is in a sensitive and/orpolicy-managed location, a certain feature of the device should bedisabled (e.g., text messaging applications or the like). At 215, it maybe determined whether an action is required based on the result of thepolicy evaluation at 212. If an action is required, the action may beperformed at 216. For example, in certain embodiments, a policy-enforcedaction may specify that certain device parameters 217 are to be set in aspecific way (e.g., parameters disabling certain device features,parameters directing the device to log certain events, etc.). If noaction is required, the process may proceed to 218.

At 218, if necessary, parameters may be set to current and/or defaultvalues and/or conditions. For example, if a feature has been previouslydisabled because of a policy determination, it may need to be reset ifthe policy is later re-evaluated and the action disabling the feature isno longer triggered. In certain embodiments, reset processes performedat 218 may be integrated into policy evaluation and enforcement steps212, 215, and/or 216.

At 219, the process may wait for a certain delay time and/or the receiptof a re-evaluation trigger before restarting the policy evaluation andenforcement steps. As discussed above in reference to FIG. 5, a user maywish to use a device in a normal manner without any policy-enforcedencumbrances after the location or contextual information associatedwith the device has changed. Accordingly, in some embodiments, theprocess illustrated in FIG. 7 may be repeated as soon as is practical(e.g., following a delay time and/or the receipt of a re-evaluationtrigger). Upon waiting the delay time and/or for the receipt of there-evaluation trigger, the process can be repeated, possibly withupdated inputs 206, 209, 213, 214 resulting in updated actions or resetdevice and/or vehicle system parameters.

FIG. 8 illustrates a flow chart of an exemplary vehicle-based method ofdetermining the presence of a device in a particular location within thevehicle consistent with embodiments of the present disclosure.Particularly, the illustrated method may determine the presence of adevice in a policy-managed location (e.g., a sensitive location) withina vehicle. The illustrated method may be implemented by a vehicle in avariety of ways, including using software, firmware, hardware, and/orany combination thereof. In some embodiments, certain aspects of thevehicle-based process illustrated in FIG. 8, may be similar to thedevice-based process illustrated in FIG. 5.

At 102, the method may be triggered. In certain embodiments, the methodmay be triggered as part of a routine start-up process of a vehicle.Alternatively, or in addition, the method may be triggered in responseto certain vehicle operations and/or based on the occurrence of aparticular vehicle event (e.g., determining that a device is withinrange of a short-range communication system in the vehicle). In furtherembodiments, the method may be triggered based on a determination by thevehicle and/or associated sensors (e.g., odometers, GPS sensors, and/orthe like) that the vehicle is in a situation where policy enforcement isdesirable. For example, the method may be triggered based on the vehicledetermining that it is moving at or above a particular speed.

At 103, the vehicle may check for signals from a short-rangecommunication system associated with a device in proximity to thevehicle and/or in proximity to a certain location within the vehicle.Checking for signals from a short-range communication system may resultin a variety of outcomes. For example, no signal(s) may be received,signal(s) may be received that do not indicate that a device is in apolicy-managed location in the vehicle, and/or signal(s) may be receivedthat indicate that the device is in a policy-managed location in thevehicle (e.g., a driver's position or other sensitive position). Basedon the received signal(s) (or lack thereof), at 104 the vehicle maydetermine whether a device is proximate to and/or within apolicy-managed location of the vehicle. If the device is in apolicy-managed location of the vehicle, sensitive location information106 may be set to indicate that a device is in a policy-managed locationat 105. If a device is not in a policy-managed location, the sensitivelocation information 106 may be set to indicate that the device is notin a sensitive and/or policy-managed location at 107. In furtherembodiments, if a device is not proximate to a policy-managed locationbut proximate to another known location, the known location may beincluded in the sensitive location information 106 set at 107 and/orstored or otherwise recorded in some other manner.

In some embodiments, the vehicle policy management system may also takeadvantage of other indicators of mobile device usage in the vehicle. Forexample, during the normal operation of mobile communication devices,signals are emitted that can be detected by the vehicle as indicative ofmobile device usage within the vehicle. By monitoring such signals, thevehicle may passively obtain information broadly indicating use of amobile device in or around the vehicle, and/or that may be used todetermine the approximate location of the device within the vehicle. Forexample, the vehicle's sensing system may contain one or more sensorscapable of receiving cellular-band communications signals and therebyable to detect the presence of an active mobile device in proximity tothe vehicle. Various characteristics of the received signal can bemonitored and used as inputs to the vehicle policy management process.For example, if the vehicle is in motion, and the signal strength of thetransmission does not vary substantially over a suitable length of timeand/or between multiple sensors on the vehicle, then the vehicleinformation system may be able to conclude that the device is being usedin the vehicle and is not in a nearby vehicle that is following intraffic. This may be particularly useful for passive monitoringapplications such as for safety audits of fleet operations vehicles of atransportation company or service vehicles. By securely monitoring andreporting on the use of mobile devices while vehicles are in use,companies can use this information to help guide safety training effortsor as supporting data for negotiating insurance rates for their fleetoperations. Depending on the sensitivity and resolution of the sensorsand their arrangement within the vehicle, differential analysis ofcharacteristics of the received signals can also be used as a means tomore accurately narrow the range of possible location of operation ofthe device within the vehicle (e.g., strength, timing, multi-path,interference, etc.). Although the foregoing example illustrated the useof these techniques in the context of a wide-area network technology,the passive data collection techniques can also be used withshorter-range communications as well, such as but not limited toon-board Wi-Fi networks, etc. Passive data collection techniquesgenerally yield less detailed information about the use of the device(e.g., whether the keyboard is active, etc.), however, in someembodiments vehicles may use such passively obtained environment data inlieu of, or in addition to, active short range communications todetermine sensitive location information.

Referring once again to FIG. 8, after the sensitive location information106 has been set, the method may proceed to 108 where the vehicle maywait for a certain delay time and/or for receipt of a re-detectiontrigger, causing the vehicle to re-check the status of the sensitivelocation (e.g., whether a device is present in the sensitive location)on a periodic and/or an event-driven basis. In further embodiments,sensitive location information 106 may be updated on an effectivelycontinuous basis (e.g., without a delay time or re-triggering event).Consistent with embodiments disclosed herein, sensitive locationinformation 106 may be used in policy management and enforcementprocesses. For example, as discussed above, certain features and/orfunctions of a vehicle and/or a device may be temporarily disabled (orenabled and/or actuated) based on the status of the sensitive locationinformation 106 in accordance with policies. In addition to sensitivelocation information 106, a device and a vehicle may exchange data thatprovides contextual information about the device and/or the vehicleand/or the status thereof. As discussed in more detail below, thiscontextual information may also be used in policy management andenforcement processes disclosed herein.

FIG. 9 illustrates exemplary generation and distribution of policy data109 to a vehicle 100 consistent with embodiments of the presentdisclosure. Policy data 109 for a vehicle 100 may articulate and/orotherwise express or enable enforcement of one or more rules orconditions relating to the use and/or function of the vehicle 100. Forexample, policy data 109 may express, encode, and/or otherwise be usedto facilitate the enforcement of, among other things, conditionsrelating to the vehicle 100 (e.g., vehicle location-based conditions,conditions relating to the use of a device within the vehicle, etc.),actions associated with the one or more conditions (e.g., disabling avehicle starter system), exceptions to actions, and/or the like.

Policy data 109 may be delivered to the vehicle 100 in a variety ofways. In certain embodiments, policy data 109 may be pre-set in avehicle 100 (e.g., by a vehicle manufacturer or dealer 900 or the like).In further embodiments, policy data 109 may be configurable via anysuitable means or combination thereof. For example, in some embodiments,policy data 109 may be set and/or configured by a user 902 a (e.g., anowner of the vehicle 100, a parent of a driver of the vehicle 100, anemployer of a driver of the vehicle 100, etc.) directly into the vehicle100 via one or more inputs (e.g., inputs associated with a telematics oran IVI system of the vehicle 100). In further embodiments, a user 902 bmay deliver policy data 109 to the vehicle via a network 600. Althoughillustrated as being directly coupled to network 600, in someembodiments, the vehicle 100 may communicate with the network 600 usinga separate intermediary device in communication with the network (e.g.,a data-enabled smartphone). In some embodiments, the separate device mayitself be policy-managed consistent with embodiments disclosed herein.

Policy data 109 may be delivered to the vehicle from a variety ofnetwork-connected entities 602 b-606, 610, 900. In certain embodiments,network-connected entities capable of delivering policy data 109 to avehicle 100 may be the same and/or similar to the network-connectedentities capable of delivery policy data to a device described above inreference to FIG. 6.

In some embodiments, policy data 109 may be delivered to a vehicle 100in combination with an application downloaded to operate on a telematicsand/or IVI system included in the vehicle 100. Policy data 109 mayfurther be delivered to a vehicle 100 directly or via the network 600 byan insurance provider, a fleet manager or other supervising entity(e.g., parents of a driver of the vehicle 100, an employer, etc.),vehicle manufacturers or dealers 900, and/or other entities (e.g., lawenforcement agencies 610 providing jurisdiction-specific policy data109).

FIG. 10 illustrates a flow chart of an exemplary vehicle policyevaluation and enforcement process consistent with embodiments of thepresent disclosure. The illustrated method may be implemented in avariety of ways, including using software, firmware, hardware, and/orany combination thereof. The illustrated process may use one or moreinputs including, without limitation, sensitive location information106, policy data 109, sensed and/or received data 113, and/or contextualdevice or vehicle data 114. It will be appreciated that in otherembodiments other combinations of these or other inputs may be used.

Sensitive location information 106 may include an indication as towhether one or more devices are located within a sensitive orpolicy-managed location of a vehicle. For example, the sensitivelocation information 106 may indicate if a device is within and/orproximate to a driver's position in a vehicle. Policy information 109may include information regarding one or more conditions used toevaluate whether an action should occur, actions associated with theconditions, exceptions to the actions, and/or the like. Sensed and/orreceived data 113 may include, without limitation, data that isgenerated by vehicle sensors (e.g., odometers, accelerometers, GPSmonitors, NFC tags, etc.) and/or data received by third parties.Contextual data 114 may include information received from a device orpart of the vehicle over a short-range communications system or othermeans that, among other things, specifies information about the deviceor vehicle status or other information that is sensed by the deviceand/or vehicle.

At 110, the vehicle policy evaluation and enforcement process may betriggered. In certain embodiments, the method may be triggered as partof a routine start-up process of a vehicle and/or by a change in any ofinputs 106, 109, 113, and/or 114. Alternatively, or in addition, themethod may be triggered in response to certain vehicle operations and/orbased on the occurrence of a particular vehicle event (e.g., determiningthat a device is within range of a short-range communication system inthe vehicle). In further embodiments, the method may be triggered basedon a determination by the vehicle and/or associated sensors (e.g.,odometers, GPS sensors, and/or the like) that the vehicle is in asituation where policy enforcement is desirable. For example, the methodmay be triggered based on the vehicle determining that it is moving ator above a particular speed.

At 111, contextual information used for policy evaluation decisions maybe read or sensed. At 112, policy logic that acts upon and/or isarticulated in policy data 109 may be evaluated. As illustrated, thisevaluation may be based, at least in part, on inputs 106, 109, 113, 114.For example, a simple policy may specify that if the sensitive locationinformation 106 indicates that a device is in a sensitive and/orpolicy-managed location, a certain feature of the vehicle should bedisabled (e.g., a starter system of the vehicle, the ability of thevehicle to exceed a certain speed, etc.). At 115, it may be determinedwhether an action is required based on the result of the policyevaluation at 112. If an action is required, the action may be performedat 116. For example, in certain embodiments, a policy-enforced actionmay specify that certain vehicle system parameters 117 are to be set ina specific way (e.g., parameters disabling certain vehicle features,parameters limiting the ability of the vehicle to exceed a specificspeed, parameters causing an audible warning sound, etc.). If no actionis required, the process may proceed to 118.

At 118, if necessary, vehicle system parameters 117 may be set todefault values and/or conditions and/or values or conditions thatreflect a current state of the vehicle. For example, if a feature hasbeen previously disabled because of a policy determination, it may needto be reset if the policy is later re-evaluated and the action disablingthe feature is no longer triggered. In certain embodiments, resetprocesses performed at 118 may be integrated into policy evaluation andenforcement steps 112, 115, and/or 116.

At 119, the process may wait for a certain delay time and/or for receiptof a re-evaluation trigger before restarting the policy evaluation andenforcement steps. A user may wish to use a vehicle in a normal mannerwithout any policy-enforced encumbrances after the sensitive locationinformation 106 or other information about the device and/or the vehiclehas changed. Accordingly, in some embodiments, the process illustratedin FIG. 10 may be repeated as soon as is practical (e.g., following adelay time and/or the receipt of a re-evaluation trigger). Upon waitingthe delay time and/or for receipt of the re-evaluation trigger, theprocess can be repeated, possibly with updated inputs 106, 109, 113, 114resulting in updated actions or a reset of vehicle system parameters.

FIG. 11 illustrates exemplary condition-based policy enforcement actionsconsistent with embodiments of the present disclosure. In certainembodiments, vehicle and/or device policies may be applied based oncertain temporal and/or environmental factors. For example, a firstpolicy may be applied if a vehicle is in cloudy conditions, whereas asecond policy may be applied if a vehicle is in sunny conditions.Similarly, as illustrated in FIG. 11, policies may be applied based on atime of day. For example, a policy associated with a vehicle 100 mayspecify that if a device is used in a policy-managed location in thevehicle 100 during daylight driving conditions, a first action may beenforced (e.g., flashing one headlight 1100 and/or taillight 1102 in aparticular pattern, flashing hazard lights, etc.). Similarly, the policymay specify that if a device is used in a policy-managed location in thevehicle 100 during nighttime driving conditions, a second action may beenforced (e.g., flashing both headlights 1100 and/or taillights 1102 ina particular pattern, dimming vehicle lights in a particular pattern,flashing hazard lights, etc.). In certain embodiments, the differentactions (e.g., the first and second actions) may be applied independentof time of day, but instead applied based on whether the vehicle'sheadlights 1100 and/or taillights 1102 are on or off at the time thepolicy is enforced. It will be appreciated that FIG. 11 is intended forpurposes of illustration, not limitation, and that any other suitablepolicy could be specified and enforced.

FIG. 12 illustrates exemplary generation and distribution of policy data109, 209 by a supervising entity 1200 to a device 200 and a vehicle 100consistent with embodiments of the present disclosure. As discussedabove in reference to FIG. 6 and FIG. 9, various entities may providepolicy data to vehicles 100 and devices 200. As illustrated in FIG. 12,certain of these entities may be a supervising entity 1200. Asupervising entity 1200 may include a parent, an employer (e.g., apublic transit authority), a fleet manager, an insurance provider,and/or any other interested party or entity.

As an example, a safety-concerned parent who wants to ensure a childoperates a vehicle 100 safely may distribute policy data 209 to achild's device 200 and policy data 109 to the vehicle 100. Thedistributed policy data 109, 209 may be used to enforce vehicle anddevice-based policies respectively consistent with the systems andmethods of the present disclosure. For example, policy data 209 may bedelivered to a child's device 200 that specifies that the device 200must be set to a safe mode whenever the device 200 determines it isbeing used in a policy-managed location in the vehicle 100. Similarly,policy data 109 may be delivered to the vehicle 100 specifying thatwhenever a device 200 is used in policy-managed location in the vehicle100, such use is logged by the vehicle 100.

In some embodiments, policy data 109, 209 may include information thatallows the vehicle 100 to identify itself to the device 200 and/or thedevice 200 to identify itself to the vehicle 100. Such identificationinformation may include information specified by the vehicle or deviceuser or administrator, or any other suitable information. In certainembodiments, such identification may provide a measure of security. Forexample, information used to authenticate the device 200 and/or thevehicle 100 may reduce the likelihood of malicious tampering with thedevice 200 or the vehicle 100. For example, a policy associated withvehicle 100 might indicate that certain actions (e.g., disabling certainvehicle functions like starting the engine in response to the detectionof a device being used in a sensitive location) can be performed only ifthe device associated with the action has been authenticated.

FIG. 13 illustrates exemplary information used in a device-based policymanagement and enforcement decision consistent with embodiments of thepresent disclosure. As discussed above in reference to FIG. 7, a device200 may use policy data 209 and/or various sensed and/or received data213 in evaluating and enforcing policies that make use of and/or arearticulated in the policy data 209. For example, the device 200 mayenforce policy data 209 that encodes or otherwise parameterizes acondition that when the device 200 is proximate to a driver's positionin a vehicle, an action such as disabling a distracting phone feature(e.g., a text messaging application or the like) should be performed.

Policies articulated in policy data 209 may further be conditioned onsensed and/or received data 213 including, for example, an operationalmode of the device. For example, the device 200 may enforce a policyspecifying a condition that when the device 200 is proximate to adriver's position in a vehicle and is not in a “voice-control only”mode, the device 200 should perform an action including switching itselfto the “voice-control only” mode. It will be appreciated that any othersuitable conditions, actions, and/or exceptions could also (or instead)be enforced by the device 200.

FIG. 14 illustrates exemplary information used in a vehicle-based policymanagement and enforcement decision consistent with embodiments of thepresent disclosure. As discussed above in reference to FIG. 10, avehicle 100 may use policy data 109 and/or various sensed and/orreceived data 113 in evaluating and enforcing policies. A vehicle 100may use sensitive position location information indicating whetherdevices are proximate to policy-managed locations in the vehicle 100and/or other sensed and/or received data 113 in evaluating and enforcingpolicies. For example, the vehicle 100 may enforce a policy specifying acondition that when a device is proximate to a driver's position in thevehicle 100 and the vehicle is moving faster than 1 MPH, an action suchas lighting a warning indicator should be performed. Similarly, thevehicle 100 may enforce a policy articulated in policy data 109specifying a condition that when a device is proximate to a driver'sposition in the vehicle 100 and the vehicle is not in park (e.g., thedrivetrain is engaged), a warning signal may be sounded in the vehicle100. It will be appreciated that any other suitable conditions, actions,and/or exceptions may also (or instead) be enforced by the vehicle 100.

FIG. 15 illustrates exemplary vehicle sensors 1500 that can be used inpolicy evaluation and enforcement processes consistent with embodimentsof the present disclosure. Vehicle sensors 1500 may provide a variety ofsensor information to a vehicle information system 1502. Vehicle sensorsmay include, without limitation, speedometers, motion sensors,short-range communications sensors/systems, parking brake sensors,transmission sensors (e.g., gear/park sensors), GPS sensors, airbagdeployment sensors, crash sensors, driver and passenger seat occupantsensors, cellular-band communication sensors, and/or any other sensorproviding sensed and/or supplemental/contextual vehicle information.

Information provided by vehicle sensors 1500 along with any additionalinformation that is available to the vehicle information system 1502 maybe provided to a vehicle policy evaluation subsystem 1504 configured toperform policy management, evaluation, and enforcement operations.Vehicle policy evaluation subsystem 1504 may use this information, atleast in part, to make policy enforcement decisions directing a vehiclecontrol subsystem 1506 to take certain conditioned actions. For example,based on a policy enforcement decision, vehicle policy evaluationsubsystem 1504 may direct vehicle control system 1506 to prevent thedrivetrain of the vehicle from being engaged and/or cause lights of thevehicle to flash in a particular pattern. Information provided byvehicle sensors 1500 may further be provided to a short range devicecommunication subsystem 1508 for communication to devices operatingwithin the vehicle as supplemental and/or contextual vehicle data.

FIG. 16 illustrates exemplary supplemental device data 220 that can beused in policy evaluation and enforcement processes consistent withembodiments of the present disclosure. Devices and vehicles may exchangesupplemental data with each other, thereby allowing for richer morecontext-sensitive policies to be evaluated and enforced. For example, asillustrated, supplemental device data 220 may be communicated to avehicle 100 by a device 200. Supplemental device data 220 may include,without limitation, device status information (e.g., power status,screen status, keyboard status, data services status, etc.), GPS dataand/or other location information, motion sensor information (e.g.,accelerometer data), device mode information (e.g., “airplane mode”,“car mode”, “voice control only mode”, etc.), information specific tocertain applications executing on the device 200, device or ownerspecific policy information, and/or the like. It will be appreciatedthat various other types of supplemental device data 220 could also beused.

FIG. 17 illustrates exemplary supplemental vehicle data 120 that can beused in policy evaluation and enforcement processes consistent withembodiments of the present disclosure. As illustrated, supplementalvehicle data 120 may be communicated to a device 200 by a vehicle 100.Supplemental vehicle data 120 may include, without limitation, vehiclestatus information (e.g., power status, powertrain status, brake status,etc.), sensor information (e.g., motion sensor data, speedometer data,crash sensor data, etc.), driver and/or occupant seat indicatorinformation, information specific to certain applications executing onthe vehicle 100, vehicle or owner specific policy information, and/orthe like. It will be appreciated that various other types ofsupplemental vehicle data 120 could also be used.

FIG. 18 illustrates exemplary sharing of contextual vehicle and devicedata 214, 114 consistent with embodiments of the present disclosure.Contextual vehicle data 214, which may be used in embodiments of thepolicy management, evaluation, and enforcement processes disclosedherein, may comprise some or all of supplemental vehicle data 120provided to a device 200 from a vehicle 100. As illustrated,supplemental vehicle data 120 may be communicated to the device 200 ascontextual vehicle data 214 using short-range communication subsystemprocesses 1802, 1800 respectively included in the vehicle 100 and thedevice 200.

Contextual device data 114, which may be used in embodiments of thepolicy management, evaluation, and enforcement processes disclosedherein, may comprise some or all of supplemental device data 220provided to a vehicle 100 from a device 200. As illustrated, thesupplemental device data 220 may be communicated to the vehicle 100 ascontextual device data 114 using short-range communication subsystemprocesses 1800, 1802 respectively included in the device 200 and thevehicle 100.

FIG. 19 illustrates exemplary policy evaluation and enforcement by avehicle 100 consistent with embodiments of the present disclosure. Asillustrated, policy evaluation and enforcement decisions by the vehicle100 may be based, among other things, on policy data 109, sensed and/orreceived data 113, and/or contextual device data 114 communicated to thevehicle 100 by a device 200. The vehicle policy data 109 may specifyand/or otherwise enable enforcement or performance of one or moreconditions, actions based on the conditions, and/or exceptions to theactions. For example, as illustrated, the policy data 109 may specifyconditions that if a driver or operator position in the vehicle 100includes a device 200, if the vehicle 100 is not in park, and if thescreen of the device 200 is activated (e.g., based on contextual devicedata 114), a safety warning buzzer should be sounded. The policy data109 may also, however, specify an exception indicating that the safetywarning buzzer should not be sounded if a crash sensor of the vehicle100 has detected a possible crash, or if airbags in the vehicle 100 havebeen deployed. In this manner, if a driver of the vehicle 100 isinvolved in an accident and trapped in the driver seat of the vehicle100, the driver may use the device 200 to call for help. Likewise, ifthe device 200 is being operated in proximity to the driver's seat, butthe vehicle 100 is in a safe state (e.g., park), the device 200 can beenabled for use without compromising safety.

The policy data 109 may further specify conditions that if a driver oroperator position in the vehicle 100 includes a device 200 and if a textmessage application on the device is activated, one headlight should bedimmed or brightened to warn oncoming traffic of a possible distracteddriver. However, if the mobile device is in a “voice control only” mode,then dimming or brightening the headlight should not occur as using thedevice 200 in the “voice control only” mode may not compromise safety.It should be appreciated that the various inputs used in policyevaluation and enforcement as well as the various conditions, actions,and exceptions illustrated in FIG. 19 are to be viewed as examples ofpossible inputs and/or policy conditions, actions, and exceptions, asmany other possible inputs and/or policy conditions, actions, andexceptions may be used in accordance with the systems and methodsdisclosed herein.

FIG. 20 illustrates exemplary policy evaluation and enforcement by adevice 200 consistent with embodiments of the present disclosure. Asillustrated, policy evaluation and enforcement decisions by the device200 may be based, among other things, on policy data 209, sensed and/orreceived data 213, and/or contextual vehicle data 214 communicated tothe device 200 by a vehicle 100. The device policy data 209 may specifyand/or otherwise enable enforcement or performance of one or moreconditions, actions based on the conditions, and/or exceptions to theactions. For example, as illustrated, the policy data 209 may specifyconditions that if a device 200 is in proximity to a driver's locationin the vehicle 100 and the vehicle 100 is not in park (e.g., based oncontextual vehicle data 214), a keyboard interface of the device 200should be disabled. The policy data 209 may also, however, specify anexception indicating that the keyboard interface should not be disabledif a crash sensor of the vehicle 100 has detected a possible crash or ifairbags in the vehicle 100 have been deployed. In this manner, if adriver of the vehicle 100 is involved in an accident and trapped in thedriver seat of the vehicle 100, the driver may use the device 200 tocall for help. Likewise, if the device 200 is being operated inproximity to the driver's seat, but the vehicle 100 is in a safe state(e.g., park), the device 200 can be enabled for use without compromisingsafety.

The policy data 209 may further specify conditions that if a device 200is being used in the vehicle 100 and seat occupant sensors in thevehicle 100 indicate that the only occupant is in the driver's position,text messaging functionality of the device 200 should be disabled.However, if a crash sensor of the vehicle 100 has detected a possiblecrash, airbags in the vehicle 100 have been deployed, or the vehicle 100is travelling less than 1 mile per hour, the text messagingfunctionality should not be disabled as the device 200 may be used underthese conditions without compromising safety. It should be appreciatedthat the various inputs used in policy evaluation and enforcement aswell as the various conditions, actions, and exceptions illustrated inFIG. 20 are to be viewed as examples of possible inputs and/or policyconditions, actions, and exceptions, as many other possible inputsand/or policy conditions, actions, and exceptions may be used inaccordance with the systems and methods disclosed herein.

FIG. 21 illustrates data distribution to and from third parties 606,612, 2100 that may be used in policy evaluation and enforcementprocesses consistent with embodiments of the present disclosure. Thirdparties may include a policy distribution service 606, a law enforcementagency 612, a geographical and/or contextual information service (e.g.,a telematics service provider) 2100, and/or any other third party orentity. As illustrated, a device 200 may communicate GPS or locationdata 221 to one or more third parties 606, 612, 2100 via network 600.The device 200 may receive data 222. The received data 222 may containpolicy information. For example, the policy information might reflectthe laws or regulations of a jurisdiction associated with the GPS orlocation data 221 and/or contextual data that may be used as inputs toan already existing policy (e.g., indications that the device 200 iswithin a no texting zone location or a required hands free operationzone or the like). A vehicle 100 may exchange GPS or location data 121and/or received data 122 to/from one or more third parties 606, 612,2100 via network 600 similarly.

FIG. 22 illustrates exemplary device and vehicle actions 2200, 2202 inresponse to policy evaluation and enforcement decisions consistent withembodiments of the present disclosure. As illustrated, device actions2200 may relate to certain functions, applications, or operating modesof a device. Device actions 2200 may further include actions relating toauto and auto-reply messaging, data logging, audible and/or visualindications, and/or the like. Vehicle actions 2202 may relate to certainfunctions, applications, or operating modes of a vehicle. Vehicleactions 2202 may further include actions relating to audible and/orvisional indications, data logging and reporting, external communicationmessaging, and/or the like. It should be appreciated that the variousdevice and vehicle actions 2200, 2202 illustrated in FIG. 22 are to beviewed as illustrative and not exhaustive, as many other possible deviceand vehicle actions 2200, 2202 may be used in accordance with thesystems and methods disclosed herein.

FIG. 23 illustrates various exemplary credentials for providing securepolicy generation, management, and enforcement consistent withembodiments of the present disclosure. Particularly, FIG. 23 illustratesvarious techniques that can be used to help guard against devices 200and/or vehicles 100 being compromised by malicious attacks. Asillustrated, a third party 2300 may communicate policy data 109, 209respectively to a vehicle 100 and a device 200. In certain embodiments,communicated policy data 109, 209 may include one or more trustedcredentials 123, 223, that may be used in securing and/or authenticatingpolicy data 109, 209 and/or other information communicated by the thirdparty 2300. In certain embodiments, the credentials 123, 223 maycomprise any suitable security and/or authentication informationincluding, for example, digital keys, shared secrets, digitalcertificates, digital signatures, and/or the like. The policymanagement, evaluation, and enforcement systems and methods disclosedherein may perform verification and/or authentication of received policydata 109, 209 and/or other information such that policies are onlyenforced if the vehicle 100 and/or device 200 determine thatcommunicated policies are trusted.

Communication between the device 200 and the vehicle 100 may use similarsecure and trusted communication techniques. In certain embodiments,identification information may be securely communicated between thedevice 200 and/or the vehicle 100 that may be further used in evaluatingand enforcing policies (e.g., using identification information toproperly log which delivery driver is in a shared truck and/or whichchild in a shared family car is using a device in an unsafe manner,etc.). In further embodiments, policy data 109, 209 may be digitallysigned and/or encrypted, and the software and/or systems used to enforcethe policy data may be secured (e.g., using any suitabletamper-resistance and/or other security techniques or technologies),thereby mitigating the potential for tampering with policy data 109, 209(e.g., by a teenager or employee that wishes to override policies set bytheir parent or employer, etc.).

FIG. 24 illustrates an exemplary system 2400 that may be used toimplement embodiments of the systems and methods disclosed herein.System 2400 may, for example, comprise a computing device such assmartphone, tablet computer, personal computer and/or a system includedin a vehicle that may perform the policy management, evaluation, and/orenforcement operations disclosed herein. As illustrated in FIG. 24, thesystem 2400 may include: a processing unit 2402; system memory 2404,which may include high speed random access memory (“RAM”), non-volatilememory (“ROM”), and/or one or more bulk non-volatile computer-readablestorage mediums (e.g., a hard disk, flash memory, etc.) for storingprograms and other data for use and execution by the processing unit2402; one or more ports and/or interfaces (e.g., a wired or wirelessinterface) 2406 for interfacing with associated sensor(s) 2412; one ormore ports or interfaces 2407 for interfacing with removable memory 2408that may, for example, include one or more memory cards, diskettes,optical storage mediums, flash memory, thumb drives, USB dongles,compact discs, DVDs, etc. and/or other computer-readable storagemediums; a network interface 2410 for communicating with other systemsvia one or more network connections 600 using one or more communicationtechnologies; a user interface 2414 that may include a display and/orone or more input/output devices such as, for example, a touchscreen, akeyboard, a mouse, a track pad, and the like; and one or more busses2416 for communicatively coupling the elements of the system 2400.

In some embodiments, the system 2400 may, alternatively or in addition,include a secure processing unit (“SPU”) 2418 that is protected fromtampering by a user of system 2400 or other entities by utilizing securephysical and/or virtual security techniques. An SPU 2418 can helpenhance the security of sensitive operations such as trusted credentialand/or key management, privacy and policy management, and other aspectsof the systems and methods disclosed herein. In certain embodiments, theSPU 2418 may operate in a logically secure processing domain and beconfigured to protect and operate on secret information. In someembodiments, the SPU 2418 may include internal memory storing executableinstructions or programs configured to enable to the SPU 2418 to performsecure operations. For example, in some embodiments an SPU 2418 such asdescribed in commonly-assigned U.S. Pat. No. 7,430,585 (“the '585patent”) and/or U.S. Pat. No. 5,892,900 (“the '900 patent”) can be used.

The operation of the system 2400 may be generally controlled by aprocessing unit 2402 and/or an SPU 2418 operating by executing softwareinstructions and programs stored in the system memory 2404 (and/or othercomputer-readable media, such as removable memory 2408). The systemmemory 2404 may store a variety of executable programs or modules forcontrolling the operation of the system 2400. For example, the systemmemory 2404 may include an operating system (“OS”) 2420 that may manageand coordinate, at least in part, system hardware resources and providefor common services for execution of various applications, and a policymanagement and evaluation module, program, or application 2428configured to implement policy management, evaluation, and enforcementfunctionality. The system memory 2404 may further include, withoutlimitation, communication software 2422 configured to enable in partcommunication within and by the system 2400, applications 2424 (e.g.,media applications), and/or policy data 2426.

In certain embodiments, the systems and methods described herein could,for example, be used in connection with security and/or digital rightsmanagement (“DRM”) technologies such as those described in commonlyassigned, co-pending U.S. patent application Ser. No. 11/583,693, filedOct. 18, 2006, and published as Publ. No. 2007/0180519 A1 (“the '693application”), U.S. Pat. No. 5,892,900, and U.S. Pat. No. 6,157,721(“the '721 patent”), and/or service orchestration or DRM technologiessuch as those described in commonly assigned U.S. Pat. No. 8,234,387(“the '387 patent”)(the contents of the '693 application and the '585patent, '900 patent, '721 patent, and '387 patent hereby beingincorporated by reference in their entireties). For example, DRMsoftware and systems such as those described in the '693 applicationand/or the '900 patent could be used in some embodiments to facilitatethe expression and enforcement of policies of the type described herein.In will be appreciated, however, that any other suitable security and/orpolicy-enforcement software, systems, and/or mechanisms could be usedalternatively or in addition.

The systems and methods disclosed herein are not inherently related toany particular computer, electronic control unit, or other apparatus andmay be implemented by a suitable combination of hardware, software,and/or firmware. Software implementations may include one or morecomputer programs comprising executable code/instructions that, whenexecuted by a processor, may cause the processor to perform a methoddefined at least in part by the executable instructions. The computerprogram can be written in any form of programming language, includingcompiled or interpreted languages, and can be deployed in any form,including as a standalone program or as a module, component, subroutine,or other unit suitable for use in a computing environment. Further, acomputer program can be deployed to be executed on one computer or onmultiple computers at one site or distributed across multiple sites andinterconnected by a communication network. Software embodiments may beimplemented as a computer program product that comprises anon-transitory storage medium configured to store computer programs andinstructions, that when executed by a processor, are configured to causethe processor to perform a method according to the instructions. Incertain embodiments, the non-transitory storage medium may take any formcapable of storing processor-readable instructions on a non-transitorystorage medium. A non-transitory storage medium may be embodied by acompact disk, digital-video disk, hard disk drive, a magnetic tape, aBernoulli drive, a magnetic disk, a punch card, flash memory, integratedcircuits, or any other non-transitory digital processing apparatus ormemory device.

Example Usage Scenarios

The following examples are provided as illustrative uses of embodimentsof the inventive body of work, and are not intended to be an exhaustivelist or otherwise limiting in any way of the systems and methodsdescribed herein.

Parental Control

With high rates of vehicle accidents and high propensity for drivingwhile distracted among teens, parents of teens may be interested in waysto mitigate the risks resulting from equipping their children withmobile phones and keys to a car. Teens are frequently given the use of aphone or a car, but often these items or the associated mobile phoneservice account are owned or controlled by their parents. In accordancewith some embodiments of the systems and methods described herein,parents can be enabled to configure their child's phone and/or vehicleto obey policies that they choose.

In an illustrative example, the mobile phone operator offers a serviceto its customers to allow devices associated with an account to beremotely configured. After logging on to her account, a mother selectsthe mobile devices of her son and daughter and applies a configurationpolicy to each of these phones. Via the cellular network, each mobilephone is configured with a policy as to how it shall behave if itdetects it is within a policy managed location in her car.Alternatively, or in addition, the parent could configure the phonesimply by downloading onto each of the phones an app designed for thispurpose from an app store, and entering his or her policy choices viathe app's user interface.

In this example, the parent selects a relatively unobtrusive policy thatwhenever the device detects that it is in a policy managed location, thedevice must (a) automatically switch into “voice-only” mode, and (b) ifthe vehicle is in motion, all text messages received will beautomatically responded to as “I am driving now, I'll get back to youlater.”

The parent also configures her car to detect devices operating withinthe driver seat, automatically pair with them and exchange data. In thisexample, the parent's car is equipped with device sensing andcommunication capabilities described elsewhere herein. In someembodiments, these capabilities could come pre-installed when the car ispurchased, or they could be installed after purchase by the parent or atechnician. For example, the parent could purchase a kit containing oneor more NFC tag stickers, and place these at appropriate locations inthe car, then download an associated app onto her family's phones tofacilitate pairing therewith and processing received data.

Returning to the example under consideration, the next day the parent'sson enters the car and sits in the driver's seat and her daughter andher friends sit in the passenger seats. After turning on the car, theson's phone immediately detects that it is in a field created by atleast one NFC antenna located in close proximity to the driver seat. Thedevice establishes a coupled link to the vehicle and receives dataindicating that it is in a policy-managed location. The device executesits policy and switches to voice-only mode. During the drive, the sonreceives a text message from a friend. Since the device still sensesthat it is in a policy managed location, and the information receivedfrom the vehicle indicates that it is in motion, the text messagereceives an automatic response as specified by the policy. Meanwhile thedaughter who is also riding in the car and carrying a phone that issimilarly configured is permitted to use the full features of her phone,because her phone is not located within the policy managed location ofthe vehicle.

As an added safety measure, an additional data item or shared secret maybe exchanged between the vehicle and the devices that is relevant forpolicy enforcement. To prevent her son's or daughter's phones from beingdisabled by a malicious or rogue installation other than in her vehicle,the mother could also optionally configure the policy with an identifierthat must also be present for the policy to be enforced. For example,when configuring the mobile phone policy, she could also enter thevehicle identification number(s) for which the policy applies. When thedevice interacts with the vehicle information system, the device canrequest the vehicle identifier and use this as an additional determiningfactor in enforcing the policy. As an alternative, a shared secret couldbe entered into both the policy and the vehicle to achieve a similarresult.

Insurance Monitoring/Verification

As distracted driving is a leading cause of motor vehicle accidents, andinsurance companies often must bear the financial cost associated withthese accidents, these organizations have a significant interest in thesafety of their customers and the vehicles they insure. As an incentivefor safe driving practices, an insurance company can offer lower ratesor rebates to customers that can submit verifiable proof that insuredvehicles are not being used by drivers who are operating mobile deviceswhile in the driver position of the vehicle. Using the technologiesdescribed herein, an insurance company can benefit from the collectionof usage information about its insured drivers and/or insured vehicles.In one embodiment, the insurance company can offer an application (or“app”) that can be downloaded or installed on the vehicle's on-boardautomotive electronics system (e.g., extensible navigation/multimediasystem, an Android™-based computer system, or the like). Usinginterfaces with the vehicle's electronic sensors and/or the vehicleinformation system, the app can register to receive data correspondingto use of devices (e.g. a mobile phone) in the policy-managed location.This data can be direct sensor data (which the app itself can analyze todetermine policy actions), or it can be data that has been at leastpartially pre-processed by the vehicle's information system thatindicates that a device is being used in a policy managed location(e.g., a warning indicator that the vehicle has activated upondetermining that a device is being operated in the driver position).

In the latter case, the automotive information system may use one ormore of the techniques described herein (e.g., near field communicationwith strategically located antennas in the driver compartment,comparative signal analysis of radio transmissions associated with oneor more vehicle mounted antennas, seat pressure indicators, vehiclespeed indicators, drivetrain status, etc.) in part or in combination todetermine whether a mobile device is being operated in a driver oroperator position. Upon making this determination, the vehicleinformation system can apply its own configured policy actions (such assounding a warning buzzer or lighting a warning indicator, etc.) andmakes data related to this determination available to apps that areloaded on the system. The insurer's app in this example receives thedetermination data and applies its own policy as to whether to take anaction in response. The application's decision as to whether take actioncan be based solely on the vehicle's determination data or incombination with other available environmental or vehicle data. Forpurposes of this example, the insurer's app uses the vehicle'sdetermination that there is a device operating in the driver position incombination with data indicating whether the vehicle is in motion. Sincethe insurer is interested in logging only unsafe actions, the app isconfigured to log data associated with the event only when there is adetermination that there is a device being used in the driver positionand the vehicle is in motion. In accordance with its policy, the appcollects additional event data such as the time and date, vehicle speed,and duration of usage in the unsafe condition. To ensure that the loginformation can be uniquely tied to a particular device, the app readsvehicle identification or customer identification information and alsoassociates it with the log data. To ensure that that the data is nottampered with after collection, the app may optionally encrypt and/ordigitally sign the collected log information, the associatedidentification information, and a random nonce before sending to theinsurer's data center. Depending on the available equipment of thevehicle, the data may be sent directly via the vehicle's on-boardcellular connection, a wireless network connection, a tetheredconnection to a nearby cellular phone, USB download, or other suitablemeans.

Employer-Managed Vehicle and Phone

A service company finds it convenient and effective to provide theiremployees with mobile phones to stay in contact with their centraldispatch while they complete their service routes. To reduce theirliability risk and ensure their employees' safety, the company wishes toadopt strict measures on the use of these phones while operating companyservice vehicles. Using techniques described herein, the companyconfigures their service vehicles with a policy that prevents thevehicle from being engaged into drive if a phone is in the driver seatand is not in a safe driving operating mode. When a driver enters thevehicle, her phone interacts with a short range communications channelin the vehicle and establishes a connection. Upon establishing theconnection, the vehicle queries the phone for information about itsoperating state. In response, the device communicates device statusinformation (such as keypad lock state, display state, etc.). If thevehicle determines that the keyboard and/or screen are in an unlockedstate, it will enforce the policy and refuse to engage the drive of thevehicle.

As an added safety measure, the company is also concerned that someemployees may attempt to unlock and use their mobile device whiledriving (after the drive has been engaged). To handle these instances,the company sets a vehicle policy to periodically poll for the devicestatus. If an unsafe device status is detected while the vehicle sensorsindicate that the vehicle is in motion, the service vehicle's hazardlights will be activated, and an event will be captured and logged forlater review.

Although the foregoing has been described in some detail for purposes ofclarity, it will be apparent that certain changes and modifications maybe made without departing from the principles thereof. It should benoted that there are many alternative ways of implementing both thesystems and methods described herein. Further, the policy management andenforcement systems and methods disclosed herein may be used in avariety of contexts that do not include vehicles. For example, withoutlimitation, in certain embodiments, systems and methods disclosed hereinmay be used to manage and enforce policies associated with certainbuildings or other locations. For example, policy management andenforcement systems and methods disclosed herein may be used to disablecertain device features (e.g., audible ringtones, backlit screens, textmessaging applications, etc.) when the device is proximate to aparticular location (e.g., within a movie theater, a restaurant, and/orthe like). Accordingly, the present embodiments are to be considered asillustrative and not restrictive, and the invention is not to be limitedto the details given herein, but may be modified within the scope andequivalents of the appended claims.

1.-9. (canceled)
 10. A method for controlling the operation of anelectronic device in a policy managed location, the steps comprising:sending policy information to a first device, said policy informationincluding one or more instructions indicating one or more operations tobe performed when said first device determines that it is located in apolicy managed location, said determination at least in part based onsaid first device receiving short range communication signals from afirst apparatus; sending policy related information to said firstapparatus, said policy related information including a validation code,said validation code to be communicated to said first device toauthenticate presence in a policy managed location within or near theapparatus; receiving, from said first device, contextual informationrelating to use of the first device while located in said policy managedlocation.
 11. The method of claim 10, wherein said contextualinformation includes information pertaining to the state of said firstdevice while located in said policy managed location.
 12. The method ofclaim 10, wherein said contextual information includes informationpertaining to the state of said first apparatus while boated in saidpolicy managed location.
 13. The method of claim 11, wherein said stateinformation indicates features of the first device that are enabled. 14.The method of claim 11, wherein said state information indicates featureof the first device that are disabled.
 15. The method of claim 11,wherein said state information describes one or more environmentalvariables present while said first device is located in said policymanaged location.
 16. The method of claim 12, wherein said stateinformation indicates features of the first apparatus that are enabled.17. The method of claim 12, wherein said state information indicatesfeature of the first apparatus that are disabled.
 18. The method ofclaim 12, wherein said state information describes one or moreenvironmental variables present while said first device is located insaid policy managed location.
 19. A method for controlling the operationof an electronic device in a policy managed location, the stepscomprising: sending policy information to a first device, said policyinformation including one or more instructions indicating one or moreoperations to be performed when said first device determines that it islocated in a policy managed location, said determination at least inpart based on said first device receiving short range communicationsignals from a first apparatus; sending policy related information tosaid first apparatus, said policy related information including avalidation code, said validation code to be communicated to said firstdevice to authenticate presence in a policy managed location within ornear the apparatus; receiving, from said first apparatus, contextualinformation relating to use of the first device while located in saidpolicy managed location.
 20. The method of claim 19, wherein saidcontextual information includes information pertaining to the state ofsaid first device while located in said policy managed location.
 21. Themethod of claim 19, wherein said contextual information includesinformation pertaining to the state of said first apparatus whilelocated in said policy managed location.
 22. The method of claim 20,wherein said state information indicates features of the first devicethat are enabled.
 23. The method of claim 20, wherein said stateinformation indicates feature of the first device that are disabled. 24.The method of claim 20, wherein said state information describes one ormore environmental variables present while said first device is locatedin said policy managed location.
 25. The method of claim 21, whereinsaid state information indicates features of the first apparatus thatare enabled.
 26. The method of claim 21, wherein said state informationindicates feature of the first apparatus that are disabled.
 27. Themethod of claim 21, wherein said state information describes one or moreenvironmental variables present while said first device is located insaid policy managed location.